Spending and savings secondary linked accounts

ABSTRACT

Embodiments describe a method and a system to link a secondary account to a primary account with an account management module associated with the primary account and to control access to funds in the secondary account with respect to a secondary account holder through the account management module. The secondary account includes a spending account and a savings account.

RELATED APPLICATIONS

This patent application claims the benefit of the filing date of U.S.Provisional Patent Application Ser. No. 60/894,875, filed Mar. 14, 2007,and entitled, “CONTROLLED SPENDING AND SAVINGS SECONDARY ACCOUNTS”, thecontent of which is incorporated by reference herein.

BACKGROUND

Dependents, employees, business associates, family members, and othersmay have a difficult time with disciplined adherence to a budget, savingfor specific items in the long-term, appropriately prioritizingspending, spending habits, and money management in general. Often, moneyis spent spontaneously such that there is often not enough money left ina budget to buy high priority items. Many are then forced to go overbudget and borrow money or take out lines of credit to pay for thesehigh priority items. In most instances, paying back the funds borrowedor taken out on credit may be difficult, expensive, and prolonged.Existing money management systems may be too conceptual, too expensive,or too restrictive.

Also, parents may not be able to appropriately discern motives of othersthat may intend to transfer funds to their children's accounts. Forexample, predators may offer to transfer funds to young account holdersas a way to gain trust from them.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention are illustrated by way of exampleand not limitation in the Figures of the accompanying drawings, in whichlike references indicate similar elements and in which:

FIG. 1 illustrates a network diagram depicting a system, according to anexample embodiment of the present invention, having a client-serverarchitecture.

FIG. 2 illustrates a block diagram showing an application server in anexample embodiment of the present invention.

FIG. 3 illustrates a high-level entity-relationship diagram,illustrating various tables that may be maintained within one or moredatabases, according to an example embodiment.

FIGS. 4 to 11 illustrate primary account administration interfacesaccording to example embodiments.

FIGS. 12 to 17 illustrate secondary account administration interfacesaccording to example embodiments.

FIG. 18 illustrates a flow chart of a method, according to an exampleembodiment of the present invention.

FIG. 19 illustrates a diagrammatic representation of a machine in theform of a computer system within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed, according to an example embodiment.

DETAILED DESCRIPTION

Embodiments describe a method and a system to link a secondary accountto a primary account with an account management module associated withthe primary account and to control access to funds in the secondaryaccount with respect to a secondary account holder through the accountmanagement module. The secondary account includes a spending account anda savings account.

In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of embodiments of the present invention. It will beevident, however, to one skilled in the art that embodiments of thepresent invention may be practiced without these specific details.

In example embodiments, a computer system (e.g., a client machine,server machine, etc.) configured by an application may constitute a“module” that is configured and operates to perform certain operationsas described herein below. Accordingly, the term “module” should beunderstood to encompass a tangible entity, be that an entity that isphysically constructed, permanently configured (e.g., hardwired) ortemporarily configured (e.g. programmed) to operate in a certain mannerand to perform certain operations described herein.

Platform Architecture

FIG. 1 illustrates a network diagram depicting a system 100 having aclient-server architecture, according to an example embodiment. Asystem, in the example form of a network-based system 112, providesserver-side functionality, via a network 114 (e.g., the Internet, apublic or private telephone network (wireline or wireless), a privatewireless network using technologies such as Bluetooth or IEEE 802.11x orother networks) to one or more clients. FIG. 1 illustrates, for example,a web client 116 (e.g., a browser, such as the INTERNET EXPLORER®browser developed by MICROSOFT®) executing on client machine 120, e.g.on a network-based device. A device application 117 may execute on aclient machine 121. A programmatic client 118 may execute on clientmachine 122. Further, while the system 100 shown in FIG. 1 employs aclient-server architecture, embodiments are of course not limited tosuch an architecture, and could equally well find applications in adistributed, or peer-to-peer, architecture system.

The client machines, including network-based device(s) 120, 121, 122,may include a mobile device, a palmtop computer, a laptop computer, adesktop computer, a personal digital assistant, a cellular telephone, acommunications device, a wireless telephone, a land-line telephone, acontrol system, a camera, a scanner, a television, television cable, atelephone with a web browser, a facsimile machine, a printer, a pager,and/or a personal trusted device. The device 120, 121, 122 may include acard, such as a smart card, a magnetic card, and/or a key card. Thedevice may include a telephone or any device capable of Short MessagingService (SMS) messaging, multimedia messaging service (MMS) messagingand/or generating audio tones, such as dual-tone multi-frequency (DTMF)tones. The device may be browser-enabled. The device may engage in aninteractive message and/or open communication session, such as SMS,electronic mail, xHTML, Wireless Application Protocol (WAP), web,interactive voice response (IVR) and/or other mobile interfaces. Thecommunication session between a client machine and the network-basedsystem may involve multiple technology modalities, e.g. the client usermay engage the system via SMS and receive a responsive communication asan SMS with an embedded hyperlinked URL directing the client user'sdevice to a WAP or web page. A hyperlinked URL may be delivered directlyto the device from the application server(s) 128 and may be used toaccess a web site or a microbrowser, such as a WAP site. The device 120,121, 122 may enable mobile videophone communications, digital televisionsignals, and/or digital radio signals. The device may include a receiverto receive near field communications as described in more detail herein.The scanner device may include a bar code reader/scanner, a RadioFrequency Interface System (RFIS) reader, and/or a symbolreader/scanner.

At least one of the devices 120, 121 or 122 may be associated with aprimary account holder. At least one of the devices 120, 121 or 122 maybe associated with a secondary account holder. In various examples, thesecondary account holder may be a relative of, a dependent of, or abusiness associate of the primary account holder.

Turning specifically to the network-based system 112, an ApplicationProgram Interface (API) server 124, and a web server 126 may be coupledto, and may provide programmatic, interfaces to, one or more applicationservers 128. The devices may use one or more of these interfaces toaccess the application server(s) 128.

For example, the web client 116 may access the application server(s) 128via the web interface supported by the web server 126. The web interfacemay include a web browser or any microbrowser, such as xHTML or WAP.Similarly, the programmatic client 118 accesses the various services andfunctions provided by the application server(s) 128, via theprogrammatic interface provided by the API server 124 and/or the webserver 126. In an additional embodiment, an application supported by oneor more applications of the application server(s) may be downloadable tothe network-based device. The device(s) may host the interfaceassociated with the one or more applications of the applicationserver(s) 128. The interface on the device may be an API interface, anSMS interface, a web interface, and/or an IVR interface. Consumerwireless device platforms, such as Java 2 Platform Micro Edition (J2ME),J2SE and J2EE allow developers to use Java and a wireless toolkit tocreate applications and programs for the device 122. The J2ME interfacemay include an application programming interface (API) for the device.The application of the programmatic client may also access the Internetusing, for example, Binary Runtime Environment for Wireless (BREW).

The device application 117 executed on the client machine 121 may accessthe application server(s) 128 via the web interface of the web server.The application 117 may be selected on the device and launched in abackground. The application 117 may additionally or alternatively accessthe server(s) 128 via the programmatic interface of the API server 124.In an embodiment, the downloaded application described herein mayinclude the device application 117.

The application server(s) 128 may host one or more administrationmodule(s) 130 and one or more payment module(s) 132. The applicationserver(s) 128 are, in turn, shown to be coupled to one or more databaseservers 134 that facilitate access to one or more databases 136. Theadministration module(s) 130 may provide for administration of variousaccounts, as discussed in more detail herein.

A third party application 138 executing on a third party server 140 maypresent offers to the account holder, such as goods and services. Thethird party may also be an acquaintance of the account holder(s), or maybe a vendor or merchant.

The payment module(s) 132 may provide a number of payment services andfunctions to users, such as client users. The payment module(s) 132 mayallow users to accumulate value (e.g., in a commercial currency, such asthe U.S. dollar, or a proprietary currency, such as “points”) inaccounts, and then later to redeem the accumulated value via severalpossible avenues, as described in more detail herein. The payment modulemay also extend credit to user, and/or may also have access to otherfunding sources to complete transactions—e.g., a credit card, a bankaccount, and/or a credit line. The payment module may operate as a moneytransmitter, for instance, and may operate using the payment module(s)132.

The third party, with whom a client user (or account holder) maytransact, may receive from the payment module(s): information regardinga requested order for a product, a service, or a donation amount,information regarding the shipment address specified by the client user,and payment confirmation. The payment module(s) may secure financialinformation of the client user with respect to the third party.

The device 120, 121, or 122 may host the interface associated with thepayment module(s) 132 of the server(s) 128. The web client 116, thedevice application 117, and/or the programmatic client 118 may beassociated with the account management module(s) 130 and/or the paymentmodule(s) 132.

The payment modules 132 may also be implemented as a standalone softwareprogram, which does not necessarily have networking capabilities. Inthis embodiment, the device may be directly connected to the paymentmodule(s) 132, without using the network 114.

The payment module(s) may have access to the database 136 having, forexample, the personal user account information through, for example, thedatabase server(s) 134. The user account information may include paymentinformation associated with the client user and an address destinationof the client user, for example.

The user account may refer to the primary account and/or to thesecondary account. When transactions are conducted from either account,the primary account holder may be considered as the contact point, forexample, a shipping address is that of the primary account holder. Theweb client 116, the device application 117, and/or the programmaticclient 118 may operate a program supported by the one or more databaseserver(s) 134. The database server(s) 134 may support one or moreaccount information links on a user interface of the network-baseddevice, for example, using the web client 116. By accessing the databaseserver(s) 134, the client user may add, amend or delete accountinformation of the client user, among other information, as described inmore detail herein, such as a default shipment address, and a defaultpayment method.

The network 114 may include a mobile telephone network, a wireless widearea network (WWAN), a wireline telephone network, a wireless local areanetwork (wireless LAN or WLAN), a wireless Metropolitan Area Network(MAN), and/or a wireless personal area network (PAN) (e.g., a Bluetooth(network). Other network-based technologies that may be used to connectinclude PON, VSAT satellite, Micro-impulse Radar, Radio Frequencyidentification (RFID), UltraWide Band, and/or Infrared. Thenetwork-based device may connect to the web using mobile internetexchange, e.g. Wireless Application Protocol (WAP) and/or HypertextTransport Protocol (HTTP).

The network 114 may allow the network-based device 120, 121, 122 tocommunicate with the third party, e.g. a vendor or a charity, and/or tocommunicate with the payment module(s) and/or the financial serviceprovider, among others having the capability to communicate through anyvarious means. The primary account holder may allow, limit or restrictsuch communications from and/or to the secondary account holder. Forexample, the primary account holder may have communications linked tothe secondary account to be approved first before being transmitted fromor received by the secondary account holder.

FIG. 1 also illustrates the third party application 138 as havingprogrammatic access to the network-based system 112 via the programmaticinterface provided by the API server 124.

Application Server(s)

FIG. 2 illustrates a block diagram showing application server(s) 128that are part of the network-based system 112, in an example embodimentof the present invention. In this embodiment, the payment module(s) 132and the administration module(s) 130 may be hosted by the applicationserver(s) 128 of the network-based system 112.

The account management module(s) 240 may be configured to set up,manage, and control the primary and secondary accounts.

The account set up module 260 may be configured to set up a primaryaccount and a secondary account linked to the primary account. Detailsof these accounts may be stored in the database tables 300, as describedbelow. The secondary account may include sub-accounts, such as aspending account and a savings account. The administration module 130may also include a primary account holder management module (accountmanagement module) 240 associated with the primary account. The accountmanagement module 240 may be configured to enable controlled access withrespect to a secondary account holder to funds in the secondary account.

The account management module(s) 240 may be configured to permit theprimary account holder to control the secondary account in various ways:ways to access funds (examples include: online, mobile payments, debitcard, send money), spending limits, spending limits in certaincategories, limit or control transfer capabilities (e.g., between thespending and saving accounts), limit or control purchase capabilities(e.g., on line layaway), limit or control deposit control (e.g., approvedeposits from different sources into secondary accounts), limit orcontrol automatic debit capabilities (e.g., a car insurance payment forinsurance that the primary user may be ultimately responsible for),limit or control automatic deposit capabilities, limit or controlpurchasing categories, limit or control purchasing merchants, limit orcontrol visibility of advertisements or marketing within an interface ofthe secondary account, and other administrative functions. In anexample, the primary account holder may be permitted to placerestrictions on fund transfers to/from the secondary account. In anotherexample, the primary account holder may suspend the secondary account,as described in more detail herein.

The primary account management module(s) 240 may also include securitymanagement module(s) 250, merchant control module(s) 252, categorycontrol module(s) 256, and marketplace control module(s) 258.

The security management module(s) 250 may be configured to managesecurity levels of the secondary account. The primary user (e.g., theprimary account holder) may monitor the security of the secondaryaccount depending upon the maturity level of the secondary user, asdiscussed herein. Security features of the account management featuresmay be discussed in more detail herein.

The merchant control module(s) 252 may be configured to manageinteractions between the secondary account and merchants. In an example,certain merchants may be permitted to transact with the secondaryaccount and/or certain merchants may be prohibited from transacting withthe secondary account, per the spending controls table 312. In anotherexample, funds available to be spent may be limited for certainmerchants per the spending limits table 314. Other merchant controlfeatures may be discussed in more detail herein.

The category control module(s) 256 may be configured to manageinteractions between the secondary account and certain categories ofgoods and services. The category control module(s) 256 may permit theprimary account holder to limit spending in certain categories, permitfund transfers for certain categories, and restrict fund transfers forcertain categories, such as alcohol or tobacco products.

In an example, the secondary account may be permitted to transact withmerchants of certain categories and/or may be prohibited fromtransacting with merchants of particular categories, per a spendingcontrols table of the tables 300. In another example, funds available tobe spent may be limited for certain categories, per a spending limitstable of the tables 300. Other category control features may bediscussed in more detail herein.

The marketplace control module(s) 258 include controlling where or howthe secondary account holder may spend funds from the secondary account(e.g., the spending account). Several examples of where/how funds may bespent are at illustrated at FIG. 13: Debit Card, Shop Online, SendMoney, and Mobile Payments. Each of these example means of sending moneymay be implemented through PAYPAL® features.

Further, the marketplace control module(s) 258 may be configured tomanage interactions between the secondary account and certainmarketplaces. These marketplaces may have prohibited merchants orcategories, for instance. In an example, the marketplace may be aparticular website, per the spending controls table of the tables 300.Funds available to be spent may be limited for certain marketplaces, perthe spending limits table of the tables 300. Other marketplace controlfeatures may be discussed in more detail herein.

A community may limit or restrict interaction between certain merchants,marketplaces, and/or URLs and the secondary users. A community basedmerchant database may be accessed by the system to evaluate where apurchase amount in a purchase request is acceptable based on thespending restrictions and controls. A secondary account may be set upwith a provision for extending the account to other groups, such as agroup of parents, a managerial group, a fraternity, a soccer team, or agroup with buying power, such as a school, and other communities thatcollectively collect and spend.

The administration module(s) 130 may include a funds transfer module 230to control transfer of funds between the savings account and thespending account. In particular, the primary user may set limits on thesecondary account user's ability to transfer funds between the savingsaccount and the spending account. See, for example, fund transfermanagement feature of account management feature described in moredetail with reference to FIG. 6.

A funds transfer module(s) 230 may include a verification/approvalmodule(s) 231. The verification/approval module(s) 231 may be configuredto verify whether the secondary account may transact given limits placedwithin the primary account holder management modules 240. Further, theverification/approval module(s) 231 may be configured to permit theprimary account holder to approve transactions with the respect to thesecondary account holder. The primary account holder may set up a securechannel for authorizing payment to/from the secondary account holder,transactions involving the secondary account holder, communicationsto/from the secondary account holder, and secondary account viewing. Theprimary account holder may set up reporting with regard to the securechannel and may set up blocks as discussed herein. Transactions may besubject to verification by the primary account holder based onconfigured rules. In one configured rule, communications andtransactions may be established by viral sign-up, for example, accountholders (primary and/or secondary) may invite communication andtransactions with third parties. If a third party has not been invited,no communications or transactions with the account holder(s) may bepermitted.

Verification and approval module(s) 231 may include analysis oftransfers to and from the secondary account, according to parameters setby the primary account holder. Transactions may be approved/disapprovedautomatically per the monitoring and approval(s) table 316 (savedentries) or they may be approved/disapproved individually, for instance.In instances where the primary account holder set to approve certain orall transactions, the transfer occurs upon such approval. Theverification module(s) 231 may communicate with a third partyapplication 138 executing on a third party server 140 to determine if anoffer by the third party still exists, if the price of the offer haschanged, and/or to determine if the product is in stock, for example.The third party may receive, from the payment module(s) and/orverification module(s): order information, shipment information, and anassociated payment and/or payment confirmation. The third partyapplication 138 may receive and process the order, send a virtualreceipt to the payment module(s) 132, and forward the order to theclient user (either or both the primary and secondary account holders),as set by the primary account holder. For services and/or donations, thethird party may receive a requested order and the payment confirmation,exclusive of the user contact information, such as a shipment address.In an additional embodiment, the service provider or charity may receiveclient user contact information and may send a receipt to the clientuser. In particular, the verification module(s) may access a databaseassociated with the third party server or associated with the databaseserver(s) 134.

A secondary account holder management module 262 may be configured toenable privacy for transactions associated with the secondary accountwith respect to the primary account. In one example, the secondaryaccount holder may control what the primary account holder may viewconcerning the secondary account. For instance, the secondary accountholder may transfer in funds from an outside funding source into theaccount and make a purchase, both of which may be unknown to the primaryaccount holder.

The secondary account may include an independent source portion and adependent source portion. The dependent source portion of the secondaryaccount may be subject to control by the primary account holdermanagement module and the secondary account holder management module.However, the independent source portion of the secondary account may besubject to control only by the secondary account holder managementmodule.

A source of the independent source portion may include funds earned bythe secondary account holder. The secondary account holder managementmodule may be configured to enable privacy for transactions associatedwith the independent source portion with respect to the primary accountholder management module. The secondary account holder management modulemay be configured to enable privacy for transactions associated with thedependent source portion with respect to the primary account holdermanagement module.

The administration module(s) 130 may include savings module(s) 264,customizing module(s) 266, store module(s) 268, navigation module(s) 270with a search module 272, reputation module(s) 274, and messagingmodule(s) 276.

The savings module(s) 264 may include an opportunity for the primaryuser to allow the secondary user to create savings goals within asavings account. The savings module 264 may be related to the savingsaccount table and the savings goal features, discussed herein. There maybe multiple savings goals that may be displayed on an interface, asshown for example in FIG. 6 herein. The savings module(s) 264 may allowautomatic payment and/or purchase of savings goals, parental control orlimits of savings goals, savings goals related to certain vendors orproviders, and dynamic price monitoring of saving goal listings. Thesavings module may be configured to enable a portion of the savingsaccount to be set aside for a selected goal, as described in more detailherein.

The customizing or personalization module(s) 266 may allow the secondaryaccount holder to customize or personalize the account with variouscolors or themes, games, budgeting tools, or other various customizationtools, as discussed herein. The budgeting tools may allow the secondaryaccount holder to monitor their own spending and to create budgets. Thecustomizing module may include a financial game module to simulate‘real-world’ savings and spending. A virtual world financial game modulemay include a fully-integrated economy architected to reward saving,budgeting and transactions. The game module may include a trackingsystem of a digital allowance sub-account.

The store module(s) 268 may allow sellers or merchants to group theiroffers within a virtual store, which may be otherwise personalized byand for the sellers. Such a store may also offer promotions, incentivesand features that are specific to and personalized by the respectiveseller. The device 120, 121, and/or 122 may be used by the client userto search the virtual store of the store module(s) for a product, aservice, a promotion, or a donation opportunity. The purchase requestfor the offer may be made through any of the devices, if permissible peraccount parameters.

Navigation of the network-based system 112, including through the storemodule(s), may be facilitated by one or more navigation modules 270. Theone or more navigation module(s) may include a search module 272. Thenavigation module(s) may enable key word searches of products, services,promotions, or donations published via the system 112. A browse moduleallows users to browse various category (e.g. music, books, offer price,shipping price), catalogue, or inventory data structures according towhich products, services, promotions, or donations may be classifiedwithin the system 112. Various other navigation modules may be providedto supplement the search and browsing modules.

The reputation modules 274 allow parties that transact utilizing thenetwork-based system 112 to establish, build, and maintain reputations,which may be made available and published to potential trading partners.Consider that where, for example, the network-based system 112 supportsperson-to-person trading, users may have no history or other referenceinformation whereby the trustworthiness and credibility of potentialtrading partners may be assessed. The reputation modules 274 allow auser, for example through feedback provided by other transactionpartners, to establish a reputation within the network-based system 112over time. Other potential trading partners may then reference such areputation for the purposes of assessing credibility andtrustworthiness.

The application server(s) 128 may include messaging modules 276. Themessaging modules 276 are responsible for the generation and delivery ofmessages to client users and third parties of the network-based system112. Such messages, for example, advise client users regarding thestatus of products (e.g., providing “out of stock” notices to clientusers). Third parties may be notified of a product order, paymentconfirmation and/or shipment information. The messaging module(s) 276may use SMS, IVR, email, or any other appropriate messaging module.Access to the messaging module(s) 276 may be granted, limited orrestricted with respect to the secondary account holder as set inparameters defined by the primary account holder. The messaging modules276 may be associated with a message feature of one of the accounts,such as message feature 1620 of the secondary account interface 1600 ofFIG. 16.

The payment module(s) 132 may include a payment transfer module 277, asavings goal purchase module(s) 278, a fraud prevention module(s) 280,and/or dispute resolution module(s) 282.

The payment transfer module 277 may transfer a payment from one of theaccounts discussed herein to the third party via the payment module(s)and/or the financial service provider. The payment may be automaticallytransferred or may be subject to approval and/or verification, asdiscussed herein.

The savings goal purchase module(s) 278 is related to the savingsmodule(s) of the administration module discussed herein. The savingsgoal purchase module(s) 278 may include the parameters to purchase,perhaps automatically, the product associated with the savings goal whenthe goal is met. This on-line layaway may satisfy an impulse to buy aproduct “now.” However, if there is insufficient funds in an account,the item may be selected for automatic payment when there is enough inthe account. In this way, the account holder does not have to rememberto purchase the item when the account has the funds. Also, havingon-line layaway may be a lesson in savings, setting goals, and meetinggoals. The merchant associated with the on-line layaway may offerdiscounts on goals listed in the savings modules and may “lock in” saleprices or offer other sales incentives. Further, the primary accountholder may offer discounts on certain purchases to the secondary accountholder (by paying the difference between what the secondary accountholder pays and the actual sales price) or the primary account holdermay provide a fund matching program to promote financial literacy.

The fraud prevention module(s) 280 may implement various fraud detectionand prevention mechanisms to reduce the occurrence of fraud within thesystem 112. The fraud prevention module(s) may prevent fraud withrespect to the third party and/or the client user in relation to anypart of the request, payment, information flows and/or requestfulfillment. Fraud may occur with respect to unauthorized use offinancial instruments, non-delivery of goods, and abuse of personalinformation. The primary account holder and the secondary account holdermay have a relationship, such as parent-child. Because the secondaryaccount holder may be a minor, contract law may not be able to beenforced. Potential fraud issues include: the secondary user maypurchase something that the parent did not approve of; there may be aseparate financial account of the secondary user; originating IPaddresses and cookies may not be consistent with previous logins; andblocking of payments from and to secondary accounts. Methods todetermine whether fraud has or is occurring include use of IP controls,and analysis of IP addresses and system cookies. The merchant/seller mayalso block access from these accounts.

The dispute resolution module(s) 282 may provide mechanisms wherebydisputes arising between transacting parties may be resolved. Forexample, the dispute resolution modules 282 may provide guidedprocedures whereby the parties are guided through a number of steps inan attempt to settle a dispute. In the event that the dispute cannot besettled via the guided procedures, the dispute may be escalated to amediator or arbitrator.

Data Structures

FIG. 3 illustrates a high-level entity-relationship diagram,illustrating various tables 300 that may be maintained within thedatabases 136 according to an example embodiment. The tables 300 may beutilized by and support the module(s) of the application server(s).

The tables 300 may include a primary account table 302. The paymentmodule(s) and/or the financial service provider may access the primaryaccount table 302 and/or may utilize the table 302 through the databaseserver(s) 134. The primary account table 302 may contain a record foreach registered primary account holder of the network-based system 112,and may include user identification information, address information(including default address), financial instrument information (includingdefault payment method, currency information), and other information(e.g. wireless carrier) pertaining to each such registered user. A usermay, it will be appreciated, operate as a seller, a buyer, a serviceprovider, and/or a service recipient, within the network-based system112.

The tables 300 may also include a secondary account(s) table 304 havinga secondary account that may be linked to one or more primary accounts.Each primary account may also be linked to one or more secondaryaccounts. Account information, similar to account information for table302, of the secondary account holder may be kept in the table 304.

Associated with secondary account table 304, may be savings account(s)table 306 and spending account table 308. A record of transactions maybe stored in the tables 306 and 308, respectively. The transactionrecord may include purchase price, the party or user with whomtransaction took, date, transaction mechanics, and other transactionrelated information.

Administration and security levels table 310 may be associated with theprimary account holder management modules 240 to administer and securesecondary accounts. The primary account holder may have management andadministrative settings stored in the table 310. The administration andsecurity levels table 310 may be used to store information concerningsecurity levels and administration and management of each primary andsecondary account. The table 310 may be associated with a monitoring andapprovals table 316, which may be associated with the spending controlstable 312 and the spending limits table 314 storing account managementdetails as described herein. Further, the security may parallel instantmessaging (IM) security measures available.

The secondary account holder may have custom ‘skin’ settings stored inthe custom skin settings table 318. Table 318 may be associated with thecustomizing modules 266 described herein. Further, budgeting tools andgames associated with the secondary account may be stored in a budgetingtools and games table 320. The budgeting tools may help teach financialresponsibility and spending discipline to the secondary users.

Interfaces

FIG. 4 illustrates a primary account holder interface 400 according toan example embodiment. The primary account interface includes useridentification information, and an ability to edit the profile of theprimary user, as well as the status of the primary user. The accounttype may be personal, business, or another appropriate type as offeredby the financial service provider. Account information may be displayedin the interface at 410. Sub-accounts or secondary accounts may also beviewed on this interface at 420. In this instance, there are twosecondary accounts, for Tommy Jr. and Samantha. There are at least onespending account and at least one savings account for each secondaryaccount. The secondary accounts may be managed and accessed by selectinga link associated with the secondary account, for example. Messagesassociated with the secondary account(s) and transactions associatedwith the secondary account(s) may be approved through use of thisinterface. An account linking feature 430 to create a new linkedaccount, to link a secondary account to a primary account, the secondaryaccount may include both a spending account and a savings account.

FIGS. 5 and 6 illustrate a management interface 500 and 600 according toan example embodiment. The primary account holder may manage thesecondary account using this interface 500 and 600. FIG. 5 illustratesthe interface in a condensed format, while FIG. 6 illustrates theinterface in an open format.

On the interface 600, there may be account management features tofacilitate automatic payments or transfers, facilitate requests formoney to be made without approval, adding funds, withdrawing funds,disabling spending accounts, disabling login accounts, disabling for acertain time period (e.g., grounded for a week), allowing transfersbetween savings and spending, funds amount limit on transfers for acertain duration, enabling spending methods (e.g., online merchant,sending funds to another email account, mobile payments, debit card,virtual debit card), funds amount limit on spending for a duration,allowing investment of savings account funds in higher interest moneymarket account, adding savings goals, and deleting savings goals.

Spending account totals and information of the secondary account may bedisplayed at spending control limit tab 510. Another account managementfeature is spending methods selection feature 610 when tab 510 is openedup. Spending methods at account management feature spending methodsselection feature 610. When opened up in FIG. 6, the spending methodsselection feature 610 may include spending methods of: online, sendmoney, mobile payments and debit card. Management of the debit card mayalso be accessed at spending methods selection feature 610.

Spending tab 510 may include several account management featuresincluding marketplace control feature 612, merchant control feature 614and category control feature 616. There may be several spending limitsassociated with different time periods, for example at accountmanagement feature: spending limit feature 620.

Savings account totals and information of the secondary account may bedisplayed at savings control limits tab 520. When opened up in FIG. 6,the Savings tab 520 may include several account management featuresincluding a fund transfer feature 630, an interest savings accountfeature 640, a savings goal feature 650, and a ‘add’ savings goalfeature 660. The fund transfer feature 630 may allow transfers from thesavings account of the secondary account to the spending account of thesecondary account.

The interest savings account feature 640 may allow funds in thesecondary account savings account to earn interest. The primary accountholder may subsidize this interest earned or may offer an opportunityfor the secondary user (holder of the secondary account) to earninterest in an account of the primary user (e.g., a money marketaccount). The interest earned in the savings secondary account may be ata different rate or a higher rate than the primary account, if theprimary account subsidizes the interest accrued.

A system of exchange and borrowing may incorporate one financialinstrument across multiple accounts. The secondary account holder mayspend from the primary account with certain restrictions. In oneembodiment, funds from multiple accounts may be combined into a single(primary) account. This fund combination may allow a merchant's or thirdparty's interface to be designed to accommodate a single account. Thecombination of funds may be handled by a secondary server of theapplication server(s) 128 associated with the secondary account(s)rather than a primary server of the application server(s) 128 associatedwith the primary account. The secondary server may manage the transferof funds from the secondary account(s) into the primary account. Accountnumber and any other relevant information for the account(s) may then beforwarded to the primary server. The payment accounts of one accounttype (for example, a savings secondary account) may be converted toanother account type (for example, the primary account) by the secondaryserver. This conversion may be transparent to both an account holder anda merchant from whom the account holder may be making a purchase. Thesystem may authorize a transaction (e.g., purchase from the merchant)and may debit the primary account according to a defined set of rules,such as reimbursing the primary account from the secondary account(s).Within this described system, the secondary account(s) may be subject tothe same interest-bearing benefits as those attributed to the primaryaccount.

The savings goal feature 650 may be associated with the savings module264 as describe herein. The ‘add’ savings goal feature 660 may be afeature to add additional savings goals.

When opened up in FIG. 6, the transfer money tab 530 may include accountmanagement features: a fund transfer feature 670 and a recurringtransfers table 680. The fund transfer feature 670 may permit theprimary account holder to transfer money between their account and thesecondary account(s), and may permit transfer of funds between thespending and savings accounts. The primary user may set parameters onfunds transfer such that approval of the primary user is met beforetransfer of funds into and out of any of the secondary accounts. Therecurring transfers table 680 lists transfers recurring with respect tothe secondary account.

When opened up in FIG. 6, the security tab 540 may include anotheraccount management feature: a security selection feature 690. Thesecurity selection feature 690 may include a sliding scale from low tohigh representing the levels of security specified for the currentsecondary account. For example, for high security levels, eachtransaction is to be approved by the primary account holder beforecompletion. Higher security levels may be recommended for youngerchildren, for instance. The security levels may restrict paying foritems on web sites that are in age sensitive categories or as notlabeled as trusted merchants. Money transactions, received and sent, aswell as messages, may be subject to approval with the highest securitylevels. With lower security levels, there may be some limits in certainfeatures, or no limits in certain features. The security features may becustomized. For example, certain categories may be turned off forpurchases, e.g., alcohol and tobacco.

The recent activity tab 550 may include a list of types of activities,to and from information for each activity, names or contact informationfor each activity, amount, date, status (completed, pending, etc.),transaction details, and actions (such as pending approvals). Theprimary user may request or view statements or reports as to secondaryaccount activity.

The interface 500 may include several account management featuresincluding an account style feature tab 560, a suspension feature 570,and a period of suspension feature 580. The account style feature tab560 may be related to the security levels that may be automatically setper account style. Security levels may also be individually adjusted.Account styles may include business, personal, and dependents, such asteens and youth. For example, there may be a college or graduate account(about age 17 and older), a teen account (about age 13 and older), atween account (about age 8 and older), and a toddler account (about age4 and older). The primary account holder may select the account stylebased on the relationship, the maturity, and/or the age of the secondaryaccount holder.

As also shown in FIG. 6, the primary account holder may suspend orenable the account status of the secondary account at the suspensionfeature 570. A “suspend until” date may also be selected by the primaryaccount holder in the event that the suspension is not indefinite, usingthe period of suspension feature 580. Access to the interface, forinstance, may be limited with respect to the secondary account holderwhen the account is suspended.

The primary account holder, e.g., the comptroller, the accountingdepartment, a parent or a supervisor, may gain a “peace of mind” knowingthat they have controls over the what, when, who and how specificationsrelated to the secondary accounts.

FIG. 7 illustrates a primary account holder interface 700 according toanother example embodiment. The interface 700 facilitates management ofa secondary account 710. Spending account information is displayed at720 in this example. The spending account information 720 may includeaccount balance, the transfer funds feature 726 and the setting limitsfeature 724. The savings account information 730 may include interestinformation 735, account balance, savings goal features 738, andassorted account management features, such as those described withreference to FIGS. 5 and 6. The account management feature of transferfund feature is depicted in this interface 700 at 745. The activitytables are broken up into money spent/spending section 750 and moneyreceiving section 760. In the money receiving section, there may be atleast one transaction pending approval at 770, as discussed in moredetail herein.

FIG. 8 illustrates a primary account holder interface 800 according toanother example embodiment. The interface 800 facilitates management ofa secondary account 810. Spending account information is displayed at820 in this example. The spending account information 820 may includeaccount balance, the setting limits feature 824 and the transfer fundsfeature 826. The savings account information 830 may be included in theinterface 800 as well. When the primary account holder selects thesetting limits feature 824, a window opens that offers several accountmanagement features. The account management features of setting limitsfeature 824 includes management of account suspension 840, management ofspending limits 850, and management of shopping destinations 860 for thesecondary account.

FIG. 9 illustrates a primary account holder interface 900 according toanother example embodiment. The interface 900 facilitates management ofa secondary account 910. Spending account information is displayed at920 in this example. The spending account information 920 may include anaccount balance, the setting limits feature 924 and the transfer fundsfeature 926. The savings account information may not be shown in thisinterface. When the primary account holder selects the transfer fundsfeature 926, a window opens that offers several account managementfeatures. The account management features of transfer funds feature 926includes management of funds transferred to the secondary account 930and management of recurring transfers to the secondary account 940.

FIG. 10 illustrates a primary account holder interface 1000 according toanother example embodiment. The interface 1000 facilitates management ofa secondary account. When the primary account holder selects the accountmanagement feature, a secondary account settings feature 1010, a windowopens that offers several account management features, includingsecondary account holder name and contact information 1020, secondaryaccount holder's bank account information 1040 to link to the secondaryaccount, and bank account information 1050 already linked to thesecondary account.

FIG. 11 illustrates a primary account holder interface 1100 according toanother example embodiment. The interface 1100 facilitates management ofa secondary account. When the primary account holder selects the“Approve?” feature, a window or feature may open that offers severalaccount management features, including a transaction approval feature1110. The transaction approval feature may offer the primary accountholder the following options: accept this payment (current transaction),accept all payments from this source (current and future transactions),decline this payment or not sure yet (i.e., do nothing or hold thetransaction until transaction approval is granted or denied). Thetransaction approval feature may include an option for the primaryaccount holder to pre-approve select transactions from a group includingselected marketplaces, selected merchants, selected categories, andselected fund transfer amounts.

FIG. 12 illustrates an interface 1200 according to an exampleembodiment. Interface 1200 shows the secondary account holder userinterface 1200 to administer the secondary account(s). A spending table1210 displays where secondary account funds have been spent and mayinclude the date associated with a particular transaction, the amount ofthe transaction and the transaction description, including category,marketplace, and/or merchant. A deposit table 1220 displays wheresecondary account funds have originated and may include date, amount,and description. If any transactions are pending approval from theprimary account holder, they may be indicated in their respective table.In this example, a pending deposit 1225 is awaiting approval.Transactions between the primary account and the secondary account(s)may be hidden at feature 1260.

Spending account information 1240 may include account balance, thespending limits, and a limits feature tab 1245. FIGS. 13 and 14illustrates a window that may open upon selection of the limits featuretab 1245. The spending limits may be listed for the secondary accountholder to view. Further, in an embodiment not shown, the spendingaccount information 1240 may indicate available spending balance (e.g.,$15 remaining of the maximum spending limit $100 this week). Shoppingdestinations or possible methods to use for spending secondary accountfunds may be listed for the secondary account holder to view. Onlineshopping may or may not be enabled for the secondary account holder,again, depending upon parameters defined by the primary account holder.To make mobile payments, for instance, the mobile phone may be activatedin this window by entering a phone number and a pin in the instancewhere mobile payments is an option provided by the primary accountholder.

Requests for funds or to send funds may be made through a fund requestfeature 1250 in the interface 1200 of FIG. 12. These fund requests maybe subject to approval by the primary account holder in certain accounttypes. The secondary account holder may send money to and request moneyfrom selected recipients or email addresses (as designated by theprimary account holder). An account settings feature 1230 may also beincluded in the interface 1200. FIG. 15 illustrates a window that mayopen upon selection of the account settings feature 1230. The accountsettings feature 1230 may include ATM card pin management, for example.Savings account information 1270 may include account balance, savingsinterest rate, and savings goals feature 1280.

FIGS. 16 and 17 illustrate secondary account holder user interfaces 1600and 1700 according to example embodiments. The interfaces 1600 and 1700may include a secondary account holder user information 1610. Thesecondary account holder user information may be editable. A messagefeature 1620 may also be part of the interfaces. A spending table 1630displays a spending balance and spending limits. Amount available, perspending limits, may also be displayed in some embodiments. A savingstable 1640 displays account balance, interest (if any), and savingsgoals features 1645. Balances and limits associated with eachsub-account (savings and spending) may be displayed. Savings goals maybe shown with appropriate icons (diploma for college, car, bicycle, MP3player, or other goal). The goal amount, and current percentage met maybe posted and/or illustrated graphically. Each savings goal may beedited, e.g., for automatic purchase. New goals may be added, and goalsmay be deleted. Each savings goals may be added to automatically uponreceipt of funds into the secondary account. For example, upon receiptof $100 into the secondary account, 10% may be automatically depositedinto a charity fund, 25% may be automatically deposited into thespending account, 5% may be deposited into each savings goal, $10 may betransferred to a car insurance payment and the rest may be deposited tosavings. The secondary account holder may have access to set thepercentages and dollar amounts automatically transferred to therespective accounts. In another embodiment, the primary account holdermay set guidelines within which the secondary account holder may budget(e.g., 0% to 25% may be deposited into the spending account).

In the instance where the primary account holder has set an appropriatesecurity level for the secondary account, the secondary account holdermay transfer funds between the secondary sub-accounts at transfer fundsfeature 1650. The secondary account holder may send funds, and/orrequest funds at the funds request feature 1660. The secondary accountholder may need to fill out the recipient or an email address as well asamount and any notes describing the transaction. The transaction may besubject to approval by the primary account holder. A table 1670 listsrecent transaction activity, as described herein. The interface 1700 maybe for a young secondary account holder with fewer options for selectionthan interface 1600. Amount of Transaction Information, icons andgraphics may be more basic, more colorful and/or playful, such as apiggy bank to represent amount in savings. A deposit table 1710 withicons representing each source may also be displayed in the interface1700.

Flowchart

FIG. 18 illustrates a flow chart of a method 1800, according to anexample embodiment of the present invention.

At block 1810, a primary account is set up using the account set upmodule 260. The primary account record is established in the primaryaccount table 302.

At block 1820, a secondary account is set up using the account set upmodule 260. The secondary account record is established in the secondaryaccount table 304. The secondary account may be set by the holder of theprimary account and may be linked to the primary account. The primaryaccount may have an account administration module to administer theprimary and secondary accounts.

At block 1830, a savings account and a spending account may be set upfor each secondary account using the account set up module 260. Thesavings account record is established in the savings account table 306.The spending account record is established in the spending account table308.

The flow chart 1800 may proceed to account management at 1840 and/or mayproceed to savings goals at 1850.

At block 1840, spending control, spending limits, and otheradministrative controls may be set up with respect to the secondaryaccount by the primary account holder. The secondary account may bemanaged, controlled, limited and/or suspended as described herein. Thecontrols and limits may be dynamic, changing as per the primary accountholder. Administrative controls record is established in theadministration and security levels table 310. Monitoring and approval(s)records are established in the monitoring and approval(s) table 316.Spending control record is established in the spending control table312. Spending limits record is established in the spending limit table314.

The primary account holder may have the account automatically changeover time or may actively change the control and limits, e.g., in theinstance where the secondary account holder is a “grounded” dependent ofthe primary account holder, the account may be suspended.

The secondary user may become a primary user upon relinquishing ofcontrols and limits by the primary user. The controls and limits may berelinquished in a graduated track, gradually relinquishing controls andlimits in a step by step fashion as time, trust, and maturity levels ofthe secondary account holder increase. The graduated track maycorrespond to the security levels designated by the primary accountholder for the secondary account. The security levels may decrease froma higher to a lower level or may increase to a higher level, forinstance, if there is an instance of friendly fraud or secondary accountsuspension. The security levels may automatically adjust, may be presetby the primary account holder to adjust if certain prerequisites aremet, or may be manually adjusted. The secondary user then may establishthe primary account with the financial service provider. The primaryaccounts of the primary user and secondary user may be linked in thesystem 112, which may provide some accessibility convenience. Forexample, when dependents leave for college, more financialresponsibility may be appropriate for parents to render. The dependentmay alternatively migrate to a type of credit card, a Campus card, oranother age appropriate fund access model, for instance.

In an instance where the secondary user earns money, at a job, forinstance, the money may be in the same secondary account, may be in anaccount linked to the secondary account, or may be in the secondaryaccount, but partitioned similar to how the savings and spendingaccounts are now partitioned, with primary-controlled ability totransfer between the sub-accounts. The financial service provider mayhave some privacy controls to allow the secondary user to block or limitaccess to the self-earned account from the primary user.

Funds may be transferred to the secondary account. The funds may be aresult of an allowance or an automatic transfer from the primaryaccount, as a one time occurrence, or on a periodic basis, as determinedby the primary user. In response to a primary account holder managementmodule of the account administration module, the funds transfer modulemay be configured control and/or limit funds transfer to the secondaryaccount from an outside source.

At block 1850, the secondary account holder and/or the primary accountholder may set up a savings goal related to purchase of goods orservices, or another goal, such as a college fund.

At block 1860, the savings goal(s) may be funded in the savingsaccount(s) of the secondary account holder.

At block 1870, upon reaching the savings goal, the goods or services maybe paid for. The goods or services may be automatically paid for, forexample, in the instance where the primary account holder has allowedsuch parameters on the account. In a further embodiment, the user may beprompted for authorization to pay for the goods or services, uponreaching the savings goal. In this embodiment, the payment is only madeupon receiving appropriate authorization from the user.

The financial service provider and/or the payment module may debit asystem account of the client user (in this case, the secondary accountholder) and credit a system account of the seller or third party. Inaddition, the financial service provider and/or the payment module maycharge the client user's credit cards, automatically withdraw funds froma bank account of the client user, or automatically withdraw funds fromcredit instruments associated with the FSP (e.g. including the PAYPAL®Buyer Credit technology). The financial service provider and/or thepayment module may pay the third party and/or vendor by depositing fundsinto a system account or a bank account of the third party. Inadditional embodiments, the payments may be peer-to-peer,business-to-business, and/or consumer-to-business. The financial serviceprovider may charge a transaction fee and/or a surcharge fee. Thetransaction and/or surcharge fee may be included in the price shown tothe client user or buyer. The payment transferred from the client usermay include the payment sent to the third party and thetransaction/surcharge fee assessed by the financial service provider.Order information and payment confirmation may be sent to the thirdparty. The order information may include shipment information.

The third party may optionally process the order, and optionally ship(or otherwise provide) the product, service, or donation, if applicable.The product and/or receipt may be physically received at the defaultaddress destination of the client user. Additionally or alternatively,the client user may receive an electronic confirmation, such as areceipt or a voucher for a service or donation, via e-mail, web pageupdate, device application update, a voicemail message, a text message,and/or a telephone message. The shipment/receipt may alternatively oradditionally be sent by the application server(s). For example, theshipment may include a message sent to the network-based device, such asa link to download an application that is ordered by the client user, amessage including a code to access a service that is ordered, or amessage including ordered information, such as stock purchaseinformation. In an embodiment where a donation is made, there may be noshipment and there may be a receipt sent to the user.

Computer System

FIG. 19 shows a diagrammatic representation of a machine in the exampleform of a computer system 1900 within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed. In alternative embodiments, themachine operates as a standalone device or may be connected (e.g.,network) to other machines. In a network deployment, the machine mayoperate in the capacity of a server or a client user machine inserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. The machine may be aserver computer, a client user computer, a personal computer (PC), atablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), acellular telephone, a mobile device, a palmtop computer, a laptopcomputer, a desktop computer, a personal digital assistant, acommunications device, a wireless telephone, a land-line telephone, acontrol system, a camera, a scanner, a facsimile machine, a printer, atelevision, television cable a pager, a personal trusted device, a webappliance, a network router, switch or bridge, or any machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine.

Further, while a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein.

The example computer system 1900 includes a processor 1902 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU), orboth), a main memory 1904 and a static memory 1906, which communicatewith each other via a bus 1908. The computer system 1900 may furtherinclude a video display unit 1910 (e.g., a liquid crystal display (LCD)or a cathode ray tube (CRT)). The computer system 1900 also includes aninput device 1912 (e.g., a keyboard), a cursor control device 1914(e.g., a mouse), a disk drive unit 1916, a signal generation device 1918(e.g., a speaker) and a network interface device 1920.

The disk drive unit 1916 includes a machine-readable medium 1922 onwhich is stored one or more sets of instructions (e.g., software 1924)embodying any one or more of the methodologies or functions describedherein. The instructions 1924 may also reside, completely or at leastpartially, within the main memory 1904, the static memory 1906, and/orwithin the processor 1902 during execution thereof by the computersystem 1900. The main memory 1904 and the processor 1902 also mayconstitute machine-readable media.

The instructions 1924 may further be transmitted or received over anetwork 1926 via the network interface device 1920.

Applications that may include the apparatus and systems of variousembodiments broadly include a variety of electronic and computersystems. Some embodiments implement functions in two or more specificinterconnected hardware modules or devices with related control and datasignals communicated between and through the modules, or as portions ofan application-specific integrated circuit. Thus, the example system isapplicable to software, firmware, and hardware implementations. Inexample embodiments, a computer system (e.g., a standalone, client orserver computer system) configured by an application may constitute a“module” that is configured and operates to perform certain operationsas described herein below. In other embodiments, the “module” may beimplemented mechanically or electronically. For example, a module maycomprise dedicated circuitry or logic that is permanently configured(e.g., within a special-purpose processor) to perform certainoperations. A module may also comprise programmable logic or circuitry(e.g., as encompassed within a general-purpose processor or otherprogrammable processor) that is temporarily configured by software toperform certain operations. It will be appreciated that the decision toimplement a module mechanically, in the dedicated and permanentlyconfigured circuitry, or in temporarily configured circuitry (e.g.configured by software) may be driven by cost and time considerations.Accordingly, the term “module” should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired) or temporarily configured(e.g., programmed) to operate in a certain manner and/or to performcertain operations described herein.

While the machine-readable medium 1922 is shown in an example embodimentto be a single medium, the term “machine-readable medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstore the one or more sets of instructions. The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by themachine and that cause the machine to perform any one or more of themethodologies of the present invention. The term “machine-readablemedium” shall accordingly be taken to include, but not be limited to,solid-state memories, or optical and magnetic media.

As noted, the software 192 may be transmitted over a network using atransmission medium. The term “transmission medium” shall be taken toinclude any medium that is capable of storing, encoding or carryinginstructions for transmission to and execution by the machine, andincludes digital or analog communications signal or other intangiblemedium to facilitate transmission and communication of such software192.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the description herein.Other embodiments may be utilized and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. FIGS. 1 to 9 are merelyrepresentational and may not be drawn to scale. Certain proportionsthereof may be exaggerated, while others may be minimized. Accordingly,the specification and drawings are to be regarded in an illustrativerather than a restrictive sense.

The following description includes terms, such as “up”, “down”, “upper”,“lower”, “first”, “second”, etc. that are used for descriptive purposesonly and are not to be construed as limiting. The elements, materials,geometries, dimensions, and sequence of operations may all be varied tosuit particular applications. Parts of some embodiments may be includedin, or substituted for, those of other embodiments. While the foregoingexamples of dimensions and ranges are considered typical, the variousembodiments are not limited to such dimensions or ranges.

The Abstract is provided to comply with 37 C.F.R. §1.74(b) to allow thereader to quickly ascertain the nature and gist of the technicaldisclosure. The Abstract is submitted with the understanding that itwill not be used to interpret or limit the scope or meaning of theclaims.

In the foregoing Detailed Description, various features are groupedtogether in a single embodiment for the purpose of streamlining thedisclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments have more featuresthan are expressly recited in each claim. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separate embodiment.

Thus, embodiments describe a method and a system to set up and controlsecondary accounts. Although embodiments of the present invention havebeen described with reference to specific example embodiments, it willbe evident that various modifications and changes may be made to theseembodiments without departing from the broader spirit and scope ofembodiments described herein.

The invention claimed is:
 1. A system comprising: an account managementmodule: to link, using one or more processors, a secondary account to aprimary account, the secondary account including a spending account anda savings account and having a dependent source portion and anindependent source portion, the account management module associatedwith the primary account, to enable a holder of the primary account tocontrol access to and use of funds in the dependent source portion ofthe secondary account with respect to a secondary account holder bylimiting spending in certain categories or with certain merchants, andto allow the secondary account holder to control funds in theindependent source portion.
 2. The system of claim 1 wherein the accountmanagement module includes a module selected from a group including asecurity management module, a merchant control module, a categorycontrol module, a marketplace control module and a funds transfermodule.
 3. The system of claim 1 including a funds transfer module tocontrol transfer of funds between the savings account and the spendingaccount.
 4. The system of claim 1 including a savings module to enableinterest to be earned in the secondary savings account.
 5. The system ofclaim 4 wherein the savings module is to enable the interest earned inthe savings account to be subsidized from the primary account.
 6. Thesystem of claim 1 including a savings module to enable a portion of thesavings account of the secondary account to be set aside for a selectedgoal.
 7. The system of claim 6 including a payment module having asavings goal purchase module to purchase a particular item associatedwith the selected goal with funds from the set aside portion of thesavings account of the secondary account upon meeting the selected goal.8. The system of claim 1 comprising a customizing module including afinancial game module to simulate ‘real-world’ savings and spending. 9.A computer-implemented method comprising: linking, using one or moreprocessors, a secondary account to a primary account with an accountmanagement module associated with the primary account, the secondaryaccount including a spending account and a savings account and having adependent source portion and an independent source portion; and enablinga holder of the primary account to control access to and use of funds inthe dependent source portion of the secondary account with respect to asecondary account holder through the account management module bylimiting spending in certain categories or with certain merchants whileallowing the secondary account holder to control funds in theindependent source portion.
 10. The method of claim 9 wherein theaccount management module includes a module selected from a groupincluding a security management module, a merchant control module, acategory control module, a marketplace control module and a fundstransfer module.
 11. The method of claim 9 including controllingtransfer of funds between the savings account and the spending account.12. The method of claim 9 including enabling interest to be earned inthe savings account of the secondary account.
 13. The method of claim 12including subsidizing the earned interest from the primary account. 14.The method of claim 9 including enabling a portion of the savingsaccount of the secondary account to be set aside for a selected goal.15. The method of claim 14 including purchasing a particular itemassociated with the selected goal with funds from the set aside portionof the savings account upon meeting the selected goal.
 16. The method ofclaim 9 comprising simulating ‘real-world’ savings and spending.
 17. Amachine-readable storage medium comprising instructions, which whenimplemented by one or more processors perform operations comprising:linking a secondary account to a primary account with an accountmanagement module associated with the primary account, the secondaryaccount including a spending account and a savings account and having adependent source portion and an independent source portion; and enablinga holder of the primary account to control access to and use of funds inthe dependent source portion of the secondary account with respect to asecondary account holder through the account management module bylimiting spending in certain categories or with certain merchants whileallowing the secondary account holder to control funds in theindependent source portion.
 18. The machine-readable storage medium ofclaim 17, wherein the operation further comprise controlling transfer offunds between the savings account and the spending account.
 19. Themachine-readable storage medium of claim 17, wherein the operationfurther comprises enabling interest to be earned in the savings accountof the secondary account.
 20. A primary account user interfacecomprising: an account linking feature to link, using one or moreprocessors, a secondary account to a primary account, the secondaryaccount includes a spending account and a savings account and having adependent source portion and an independent source portion; and anaccount management feature to enable a holder of the primary account tocontrol access to and use of funds in the dependent source portion ofthe secondary account with respect to a secondary account holder bylimiting spending in certain categories or with certain merchants, theaccount management feature further to allow the secondary account holderto control funds in the independent source portion.
 21. The primaryaccount user interface of claim 20 wherein the account managementfeature is selected from a group including a security managementfeature, a merchant control feature, a category control feature, amarketplace control feature, and a funds transfer feature.
 22. Theprimary account user interface of claim 21 including a funds transferfeature to control transfer of funds between the savings and thespending accounts.
 23. The primary account user interface of claim 20including an interest-bearing savings feature to enable interest to beearned in the savings account of the secondary account.
 24. The primaryaccount user interface of claim 23 wherein the interest-bearing savingsfeature is to enable the interest earned in the savings account to besubsidized from the primary account.
 25. The primary account userinterface of claim 20 including a savings goal feature to enable aportion of the savings account to be set aside for a selected goal. 26.The primary account user interface of claim 25 wherein the savings goalfeature is to purchase a particular item associated with the selectedgoal with funds from the set aside portion of the savings account uponmeeting the selected goal.